Method and apparatus for creating data transformation routines for binary data

ABSTRACT

A method and apparatus is disclosed for creating data transformation routines for transforming data from a source format to a target format. The routines can be used in conjunction with dynamic binary translators, which enable binaries of a source platform to execute on a target platform without recompilation. This is achieved by runtime (on-the-fly) translation of source machine instructions into equivalent target machine instructions. Typically dynamic binary translators are used for migrating from an older platform to a newer one, implementing complex instruction set architectures, speeding up simulators and in profiling tools. The transformation routines are also used for translating data in databases from one format to another, for example, where the data format has been modified in an upgraded system. In all these applications, the speed and accuracy of translation need to be kept low to ensure that the overhead incurred does not outweigh the advantages of translation.

FIELD OF INVENTION

The present invention relates to a method and apparatus for creating data transformation routines for binary data. More particularly, but not exclusively, the present invention relates to a method and apparatus for creating routines that are used dynamically by a translator, which translates software code or data from one format to another.

BACKGROUND OF THE INVENTION

The term platform is used to refer to a processor/hardware and operating system combination. Binary translators allow binaries built for a particular platform (source) to execute on another platform (target) by translating the machine instructions present in the binary code into equivalent instructions of the target platform. Binary translation can be performed either statically, wherein a new binary image is created for running directly on the target platform, or dynamically wherein the translation takes place while the binary is executed. Different types of binary translators are described by Erik R. Altman, David Kaeli, and Yaron Sheffer, in “Welcome to the Opportunities of Binary Translation.”, IEEE Computer, 33 (3), March 2000, pp 40-45.

The translated code produced by such translators is native to the processor on which it is to be run and as such, can provide performance close to native compiled binaries. However, for this to be the case the cost of translation, which is an overhead on the runtime of the binary needs to be minimised while not compromising on quality of generated code. M. Probst discusses this further in “Fast machine-adaptable dynamic binary translation.”, Proceedings of the Workshop on Binary Translation, Barcelona, Spain, September 2001.

Translation is also carried out in other scenarios, such as when databases are upgraded. In some database upgrades, data from the old system is used by the new system. However, while the data format may remain the same, there are commonly changes made to metadata format, that is, the description of how data is stored in the database. Such changes may be made to add new features to the new system.

A significant part of the process is the transformation of data from the source format to the target format in a process referred to as bit filling. In known systems, whenever bit filling is carried out, the process typically involves the following steps:

-   -   a) Shift the required bits into the target position.     -   b) Mask out those bits, which are not required     -   c) The bits in the target corresponding to those bit positions         where the new bits have to be copied into need to be cleared.     -   d) The source bits are copied into the target by an OR binary         operation.

If the source format bit sequence is such that it needs to be split up and copied into different positions in the target, then the steps above need to be carried out for each subset of bits that are to be copied into a unique location in the target. This results in a significant performance loss. Also, the source bit patterns may need to be split and copied into various target element slots, thereby further reducing performance.

A known solution to bit filling for program translation is inline assembly, which is provided by some compilers. This facility enables the user to code efficient assembly routines into the otherwise high-level language code. However, this solution is platform specific, and requires the programmer to know the instruction set architecture of every processor on which the binary has to execute. Furthermore, inline assembly can restrict possible compiler optimizations.

Transforming data by bit filling during program or database translation is a complex task, which can be carried out automatically. However, the systems available for this are difficult to build and maintain and are also error prone. The result of this is that translated programs run less efficiently and database conversions are less effective.

It is an object of the present invention to provide a method and apparatus for creating data transformation routines for binary data, which avoids some of the above disadvantages or at least provides the public with a useful choice.

SUMMARY OF THE INVENTION

According to a first aspect of the invention there is provided a method for creating data transformation routines for binary data for transforming the data from a source format to a target format, the method comprising the steps of:

-   -   a) generating a source model of a source format element;     -   b) generating a target model of a target format element;     -   c) generating a mapping between the source model and the target         model;     -   d) generating a transformation routine based on the mapping for         extracting data from the source element and depositing the data         in the target element.

Preferably the target models are generated for a plurality of target elements and a mapping generated between the source model and the plurality of target models. Preferably the source models are generated for a plurality of source elements and a mapping generated between the plurality of source models and the target model. Preferably the transformation routine is arranged for transforming data in software code instructions from a source format code to a target format code and the routines are generated in the target format code.

Preferably the mapping accounts for differences in endianness between the source and target models. Preferably the transformation routine is executed at the runtime of a program in the source code. Preferably the models relate bit positions to variable names for any given instruction. Preferably a group of source models and target models are provided wherein one or more models are applicable to a plurality of respective source or target instructions. Preferably the transformation routine is associated with a template providing a set of target format instructions semantically equivalent to the identified source instruction. Preferably the transformation routine is arranged for transforming data from a database between a source database format to a target database format.

Preferably the method is provided by a computer program for transforming data from a source instruction to a target instruction. Preferably the transformation routines are implemented as routines in the computer program. Preferably the computer program is operable to carry out the transformation at the runtime of a program in the source code.

According to a second aspect of the invention there is provided apparatus for creating data transformation routines for transforming data from a source format to a target format, the apparatus comprising:

-   -   a) a source model of a source element;     -   b) a target model of a target element;     -   c) a mapping between the source model and the target model;     -   a) a routine generator for generating a transformation routine         based on the mapping for extracting data from the source element         and depositing the data in the target element.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:

FIG. 1 is a schematic illustration of a template based dynamic binary translation process;

FIG. 2 is a table illustrating the format of an instruction for input to the process of FIG. 1;

FIG. 3 is a table illustrating variants of the format of the instruction of FIG. 2;

FIG. 4 shows a template used in the translation process of FIG. 1;

FIG. 5 shows a code routine used in the translation process to transfer data from an input instruction into the set of output instructions;

FIG. 6 shows a code routine used for defining dependence information for optimising translated code for use in a parallel processing execution environment;

FIG. 7 is a table showing the translation speed performance of a template based DBT against a conventional DBT; and

FIG. 8 is a table showing application program performance of a template based DBT against a conventional DBT.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT OF THE INVENTION

FIG. 1 shows the template based dynamic binary translation system 101 in which instructions in a source code format 103 are input into the DBT 105 and output as translated target code format instructions 107 for processing on a target processor. The system 101 includes a set of templates 109 which are used by the DBT to map instructions in the source format to a set of instructions in the target format. A fill and analysis routine generator 111 uses the templates 109 to generate a set of fill and analysis routines 113, which will be described in further detail below. The templates and the fill and analysis routines are compiled along with the translator to produce the working DBT.

The DBT in the present embodiment is arranged to translate between PA-RISC and Itanium™ assembly code formats. HP™-UX (a version of Unix from Hewlett Packard) is based on PA-RISC 2.0 processors. Itanium™ assembly code is used with Intel's 64 bit Itanium™ processor (see Intel Corp., Itanium™ Architecture Software Developer's Manual, February 2000, URL http://developer.intel.com/design/Itanium™/family.).

For any given hardware architecture, machine instructions can be divided into two distinct parts. The first part is the control part that determines the action the hardware would perform while executing the instruction. FIG. 2 shows the format of the ADD instruction from the PA-RISC assembly code. The opcode, sub-opcode, condition, width and direction fields constitute the control part of ADD instruction. These fields can have a fixed set of values and permuting them with different values generates all valid variants of the ADD instruction that can appear in PA-RISC binary code. There are 160 variants of the ADD instruction each with a different semantics. However, for sub-opcode field, not all combinations are supported in hardware, as noted in the PA-RISC instruction manual by Gerry Kane, PA-RISC 2.0 architecture, Prentice Hall, 1996. FIG. 3 shows some of the possible variants of the PA-RISC ADD instruction.

The second part of the instruction is the data part, which comprises register numbers, encoded immediate values etc, which are specific to each instance of an instruction. For the ADD instruction in FIG. 2 the data parts are the register numbers for two sources and one target register. The number of valid values that the data part can contain is from a much larger set than those for control part. For example, a 22-bit immediate data field may contain any of 222 values. These values are not known until the translator encounters a particular instance of the instruction.

The control part of all instructions in the source format instruction set is known statically, that is prior to the run time of translated code. Using this fact it is possible to list all variants of the entire input instruction set and for each variant construct a translation in the target platform instructions set. These translations are represented in the templates, which capture the semantics of the input instruction without specifying the data parts. In the present embodiment, the templates are written as Itanium™ assembly language routines. These routines are accessed through a table, which maps a unique id for each instruction variant to the corresponding template.

In the PA-RISC instruction set, the number of instruction variants is about 2600 and each requires a template and a corresponding data fill routine. As noted above, the fill routines extract the various data parts from the input instruction and deposit them into the template. The fill routines are constructed automatically by a process that analyses the templates using the source and target binary instruction formats. This process is described in further detail below.

FIG. 4 shows the template for the ADD instruction variant “ADD, L, =r1, r2, t” in Itanium™ assembly. This variant performs logical addition (without carry) of register r1 and r2 and places the result in register t. Additionally, if the result is 0, then the next instruction is nullified. In the assembly code in FIG. 4, the first instruction performs the addition, while the second sets predicate registers pT to 0 and pF to 1 if the result register is equal to 0. These predicate registers are used to nullify the next template.

During translation, the fields PA_r1, PA_r2 and PA_t are filled with the source and target operands from the input instruction. These fields correspond to the PA-RISC register mapped as native registers of Itanium™ (see C. Zheng and C. Thompson. PA-RISC to IA-64: Transparent execution, no recompilation. Computer, 33(3): 47-52, March 2000). Also the fields pT and pF are filled with those predicate registers that are used for nullifying the next template. In the present embodiment, in order to compile the template into the DBT, dummy values are used for all the fillable positions.

The template contains meta-data used in the generation of the fill routines. For example, the template in FIG. 4, the name of the template “template_ADD_L_EQ” identifies the PA-RISC instruction completely. The second line contains a label with the keyword “magic_<template-id>”. Template-id is a unique number obtained by concatenating the various control parts of ADD, L, =r1, r2, t. The translator constructs the template-id from the input instruction and uses that to identify the correct template and fill routine.

Compared to conventional binary translation, template based translation progresses as follows:

-   -   Extract from input instruction its control part to form a unique         template ID     -   Populate the template identified by this ID using data parts         from input instruction     -   Perform optimization (e.g. code scheduling) on populated         template     -   Emit the optimized code to translation cache         Generating the Fill Routines

The fill routine generator 111 identifies the fillable positions within a template by parsing it, and generates code to extract and deposit the fields from input PA-RISC instruction into the precompiled Itanium™ template. In cases where the input field does not come from the PA-RISC instruction, such as the predicate registers or temporary registers, the generated code contains references to translator internal data or register allocators.

To generate the extract and deposit code the fill routine generator uses information on the instruction encoding formats of the source and target machines captured in tables. Each source and target instruction name is mapped to the appropriate encoding format. The fill routine generator also takes in to differences in endianness, for example, PA-RISC binary contains instructions in big-endian format whereas Itanium™ pre-compiled templates are stored in little-endian format. In addition, HP™-UX operates in big-endian mode on Itanium™ processors. While converting each Itanium™ bundle into big endian, depositing the fillable positions and converting back into little endian is possible, but not preferred due to the high latencies involved in such conversion. Instead, the fill routine generator is arranged to compute the bit positions of operands apriori after conversion into little endian format.

When bit-filling runtime operands into precompiled machine code it is important that the operation incurs minimum cost with respect to time. Carrying out the minimum number of operations when extracting the source operands and depositing them into the required bit positions in the target code helps to achieve this minimum cost. In the DBT, the bit-filling operation has the following basic steps:

-   -   a) Extract runtime operand value from instruction being         emulated.     -   b) Calculate the target bit positions (or sets of bit positions)         where the operands have to be bit-filled.     -   c) Fill the bits into the positions identified in step (b)

Itanium™ hardware offers extract ‘extr’ and deposit ‘dep’ instructions that are used by the fill routines to efficiently extract PA-RISC operands and deposit them into the Itanium™ template. In order to ensure that these instructions are actually generated by the compiler the fill routine code is written as illustrated in FIG. 5. The operand bit positions being accessed are expressed as a bit-field within an unnamed structure type casted on the data item containing the Itanium™ or PARISC instruction. Accessing field “f” on RHS of the C statement in FIG. 5 causes an ‘extr’ instruction to be generated by the compiler from bits 20:25 of “pa_instr”. Similarly on LHS, a ‘dep’ instruction is generated for bits 10:15 of “ia_instr”. Since the field widths within the unnamed structure are computed automatically, the fill routine code is highly reliable. This technique leads to significant performance gains in template filling further reducing the translation overhead.

In the DBT of the present embodiment the PA-RISC instruction streams are read, the runtime values are extracted from them and filled into a set of Itanium™ (IA64) instructions. The DBT is implemented in the C language and so C language structures are used to implement the bit-filling mechanism. All the PA-RISC instructions are modeled as C data structures so that the total size of the structure is the same as the size of the instruction, which is 32 bits for PA-RISC. Each component of the instruction is defined as a separate member of the data structure (or struct). For example, the PA-RISC ADD instruction has the following format: Bits 6- 11- 16- 22, 24, 27- 0-5 10 15 18 19 20 21 23 25 26 31 02 R2 R1 C F E1 1 E2 0 D t

This instruction results in t=r1+r2. This instruction is modeled in C as: typedef struct pa_format_8 { u32 PA_op:6; u32 PA_r2:5; u32 PA_r1:5; u32 PA_pad:11;/* all control bits, not operands */ u32 PA_t:5; } pa_format_8;

Similarly, the IA-64 instructions are modeled as a structure. But since the IA-64 is not a RISC processor, the structure formation is not as simple. The IA-64 instruction stream consists of a sequence of “bundles” each of which is 128 bits wide, and contains three IA-64 instructions each of which is 41 bits wide and occupies one of the three “slots” in the bundle. The remaining 5 bits define the bundle type. Also, subject to certain restrictions any instruction can be in any position in the bundle e.g. an IA-64 add instruction could be in slot 1, 2 or 3 in a Memory Memory Integer (MMI) type bundle. The format of a IA-64 add instruction is as below: Bits 40 to 38 37 to 21 20 to 14 13 to 7 6 to 0 Precompiled (pcd) R3 R2 R1 Qp

The semantic of the above instruction when precompiled as an ADD instruction is r1=r2+r3 if qp==TRUE. The next step is to map PA_r1 into r2, PA_r2 into r3 and PA_t to r1. Since the IA64 is little endian, these instructions are arranged in memory as shown below for slot 1 (the same logic can be used to extrapolate the positions for slot 2 & 3): Byte 1 Byte 2 Byte 3 Byte 4 Byte 16 [r1(1:0)| [r2((2:0)| [r3(3:0)| [PCD| [. . .] qp(0:5)] r1(6:2)] r2(6:3)] r3(6:4)]

Since C language allows individual variables to be a maximum of 64 bits wide, the above 128-bit bundle is modeled as two 64-bit structures. The first structure is modeled as: struct Bundle_0_63 { u64 r1_1_0:2; u64 qp :6; u64 r2_2_0:3; u64 r1_6_2:5; u64 r3_3_0:4; u64 r2_6_3:4; u64 pcd_1 :5; u64 r3_6_4:3; /* \ * |Bundle 2 * |data */ / }

The final size of this structure is 64-bits and it mirrors the first 64-bits of a bundle. Therefore, the C code for extracting and depositing the values of PA_r1, PA_r2 and PA_r3 into the IA-64 bundle at runtime is:

-   -   ((struct Bundle_(—)0_(—)63 *)IA_(—)64_bundle_(—)0_(—)63)−>r1         _(—)1_(—)0=((pa_format_(—)8 *)PA_instruction)−>PA_t;     -   ((struct Bundle_(—)0_(—)63 *)IA_(—)64_bundle_(—)0_(—)63)−>r1         _(—)6_(—)2=((pa_format_(—)8 *)PA_instruction)−>PA_t>>2;     -   ((struct Bundle_(—)0_(—)63 *)IA_(—)64_bundle_(—)0_(—)63)−>r2         _(—)2_(—) 0=((pa_format_(—)8 *)PA_instruction)−>PA_r1;     -   ((struct Bundle_(—)0_(—)63 *)IA_(—)64_bundle_(—)0_(—)63)−>r2         _(—)6_(—)3=((pa_format_(—)8 *)PA_instruction)−>PA_r1 >>3;     -   ((struct Bundle_(—)0_(—)63 *)IA_(—)64_bundle_(—)0_(—)63)−>r3         _(—)3_(—)0=((pa_format_(—)8 *)PA_instruction)−>PA_r2;     -   ((struct Bundle_(—)0_(—)63 *)IA_(—)64_bundle_(—)0_(—)63)−>r2         _(—)6_(—)4=((pa_format_(—)8 *)PA_instruction)−>PA_r2>>4;

The compiler is arranged to issue only an extract and a deposit even when there are shifts present in the C code, by adjusting the extract position. In this way, we can use standard high-level language structures to enable the compiler to generate efficient code for moving some bits from one location to another.

DBT Build and Operation

The build and compilation process of the DBT is summarised as follows:

-   -   1. Create a repository of magic numbers. As noted above, a magic         number is a unique integer that represents one and only one         variant of a source instruction. The collection of all the magic         numbers represents the set of all valid instructions possible of         the source instruction set. The result of this stage is a set of         constants associating a unique string with a unique integer,         wherein the string shortly describes the instruction variant,         which the magic number is supposed to represent.     -   2. Create a template repository. As noted above a template is a         functionally equivalent sequence of target architecture         instructions, for each source instruction. A template assumes         temporary native registers for its operations and is compiled         (at DBT's compile time) as a function whose name will be derived         from the corresponding magic number's associated string         mentioned in 1 above. The templates are available as a         routine/function at run-time.     -   3. Create a table, indexed on magic numbers, containing the         references to the corresponding templates. At run-time the         translator picks up the appropriate template for a given         instruction after ascertaining its magic number as described         below.     -   4. Create template filler routines repository in which each         template filler routine (TFR) has the knowledge of both the         source and target instructions. The TFR of a given template         extracts the dynamic components of the source instruction         (registers, immediates etc) and fills the extracted items in the         in-memory template to replace the corresponding “place-holders”.         The translator calls the TFR for a given instruction at         run-time. The TFR repository is linked to corresponding         templates and magic numbers.     -   5. Create minimal decode/magic-number-extractor routines         repository (MNE routines). An MNE routine, given a raw source         instruction, returns the magic number of that instruction. Each         MNE routine is written in assembly by hand for maximum optimity.     -   6. The resources in steps 1 to 5 are compiled together to         prepare the DBT. At run time the DBT carries out the following         steps:     -   a) DBT receives a source instruction Si.     -   b) DBT maps the Si to appropriate MNEi and calls MNEi with Si as         a parameter.     -   c) MNEi returns magic number mi.     -   d) DBT maps mi to template ti.     -   e) Copy ti to the code generation buffer b (in-memory).     -   f) DBT maps mi to TFRi.     -   g) DBT calls TFRi and passes to it b and Si as parameters. (The         TFRi extracts dynamic components of Si and fills in the ti found         at address b).     -   h) Go to S(i+1) if the current block is not yet finished (block         end may be defined as needed by the user. Generally a control         transfer instruction such as a branch or a jump ends a         block—called basic block in compiler terminology).     -   i) Optimise the sequence of instructions in the buffer b for         best temporal performance.     -   j) Emit optimised code from buffer b to code cache Ci where the         instructions will be processed by the processor.         Generating Analysis Routines

The templates contain dependency information that is used in a code scheduler for the generated code. The scheduler exploits the multiple issue capabilities offered by the Itanium™ hardware, that is the parallel processing capability. Apart from the fillable fields, each template is complete in terms of data dependencies (Read-After-Write (RAW), Write-After-Write (WAW) and Write-After-Read (WAR)) and the bundling requirements of Itanium™. As a result, the analysis routine generator 111 can generate code statically for use by the scheduler in dependency analysis. The generated routines are called analysis routines.

With reference to FIG. 4, the resource PA_t, of the second instruction has a Read-After-Write (RAW) dependency on the first instruction irrespective of the value of PA_t. This invariant is identified by the analysis routine generator, thus saving the cost of determining this dependency at runtime. The scheduler represents dependency information using a Directed-Acyclic-Graph (DAG) and therefore the analysis routine generator generates code that adds a RAW edge between the nodes for first and second instruction.

The analysis routine generator does not have access to some values such as those of PA_t, PA_r1 and PA_r2. In this case the analysis routine generator generates dependency analysis code using input and output resources named in the template. For example, in FIG. 4, code to add a RAW edge between the last producer of PA_r1 and the first instruction is generated. Similarly code to add a Write-After-Write (WAW) edge between the last producer of PA_t and the first instruction is also generated. Such code discovers all dependencies without having to identify the input and output resources of an instruction at runtime.

FIG. 6 shows the output of the analysis routine generator 111 for the template ADD_L_EQ shown in FIG. 4. The code speeds up dependency analysis in the Itanium™ code scheduler. This code identifies a significant subset of dependencies within instructions in a single template and generates appropriate DAG edges. The code for complete dependency analysis does not attempt to determine the input/output set of instructions being analyzed, since this information is already available to the fill and analysis routine generator.

The analysis routine generator carries out the following process:

-   -   1. Invokes the analysis routines for each translated template.     -   2. The analysis routine performs dependency analysis and assigns         each instruction into the earliest group (Instruction Group in         Itanium™ terminology) respecting all dependencies. A Group is         defined as a set of instructions, all of which can be issued in         parallel.     -   3. For each group, construct the instruction bundles for         parallel issue according to Itanium™ rules.     -   4. Emit the bundled code into the translation cache for         execution.

Using the generated analysis routines saves the cost of figuring out input/output sets of instructions being analyzed. Further, code in analysis routine is optimum because it is constructed by examining the specific instructions being scheduled from the template. In other words, the analysis routines are a specialization or partial evaluation of the code for a traditional scheduler using the templates as input. Since the collections of templates form the complete set of inputs to the scheduler, this system is correct and complete.

In an alternative embodiment, the step of building the DAG is omitted. Instead, a counter is kept and is associated with each instruction to indicate the group number to which the instruction belongs. This counter is incremented every time an edge is discovered. The counter computes the earliest group to which a given instruction can be assigned such that all producers of its input (for RAW) and output (for WAW) resources have already been assigned to previous groups. The basic algorithm is given in the following expression: Group(instr1)=max{Group(last _(—) producer[Res])\Res _(—) Input(Instr1) U Output(instr)}

This embodiment offers a lightweight and fast scheduler for Itanium™ that works with template based translation.

Optimisations in Template Based Translation

Template based dynamic binary translation creates opportunities for optimizations by speeding up the basic translation process. Using template-based translation it is possible to employ a fast translator with minimal optimizations. Alternatively, with same translation cost as that of a conventional DBT, more sophisticated optimizations can be targeted.

In a further embodiment, apart from scheduling, peephole optimizations that need pattern matching are performed. Some target architectures offer a single instruction to complete a task that takes multiple instructions on the source architecture. One such case is division operation in PA-RISC code, which requires a long sequence of divide-step (DS) instructions. However, on Itanium™ the sequence of DS instructions can be replaced by a much shorter sequence using floating-point reciprocal approximation (FRCPA) instructions. To detect a pattern of DS instructions from the input instruction stream is a heavyweight operation in a conventional DBT because to detect a pattern in machine instructions, the control part of input instructions must be matched to a known sequence. In conventional translation this needs to be separately constructed whereas in the present embodiment with template based translation, the stream of unique template-ids from input instructions are matched against the known sequence.

Template based translation proceeds with minimal decision points because a onetime construction of the template-id is sufficient to determine which instructions to emit. In a conventional translator, instruction selection happens by examining bits within the input instruction in a hierarchical manner leading to many control transfers. The ability to deal directly with precompiled binary code removes the conventional need for an intermediate representation (IR) and conversion from the IR to binary format. However, removing the IR can severely restrict ability to perform analysis and optimizations at translation time. Embodiments of the invention alleviate this restriction by using the static representation of the template as the IR and using the analysis routine generator to generate code for performing optimizations. This generated code can be treated as a partial evaluation or specialization of similar code in a conventional optimizer. Since the collection of all templates form the entire set of inputs to an optimizer, such specialization leads to optimal and complete code.

Performance of Template Based Translation

FIG. 7 shows data, which provides a comparison of the performance characteristics of an embodiment of the invention against a conventional DBT. The data shown is without scheduling using a computer with a 4-way Itanium2™ processor running at 900 MHz with 8 GB of physical memory. Since template based DBTs offer high-speed translation, one key measure is the average number of CPU cycles consumed by the translator to translate one input instruction. This is measured with different types of applications:

-   -   Simple utilities such as Is, tar, gzip, ghostscript™;     -   Computationally intensive programs from the SPEC2000 suite;     -   Java Virtual Machine™ (JVM) using the SPECJVM98 suite; and     -   I/O intensive applications like Netscape™.

From the data in FIG. 7 it can be seen that with the template based translation, there is an average reduction of 4 to 5 times in translation overhead across a spectrum of applications. Although all applications show significant gain in translation overhead, the performance gained in total runtime depends on the ratio of translation overhead to the total runtime. Data for this is shown in FIG. 8. For compute intensive SPEC2000 applications the gain is minimal, as for these applications translation time is a very small percentage of total runtime. However, for Java™ applications from SPECJVM98 suite, translation time is a significant portion of total runtime. In case of JVM and Java™ applications, there is a gain of 250% to 400% on the total runtime. For one application ‘_(—)209_db’ from SPECJVM98 suite, the gain is as high as 700%. Although the gain in Java applications is accentuated by the frequent translation-cache flushes caused by JVM, it is independent of the algorithm used to decide if a flush is required. For other applications the gain ranges from 0 to 300%. There are some applications like ‘gcc’ and ‘gzip’ that perform poorer than the conventional DBT. This is due to analysis like d-u chain analysis for carry-borrow bit updation.

One of the problems in dynamic binary translation is the cost of translation and optimization over execution of the translated code. The problem is particularly severe in applications that have poor code locality or frequently cause a translation-cache flush. Template based translation offers significant reduction in translation overhead without compromising code quality or flexibility to perform optimizations. It also facilitates automatic generation of optimized fill and analysis routines.

From the above description it can be seen that the heavyweight instruction selection stage of a conventional DBT is replaced by a lightweight phase of populating the selected template, which is a series of bit filling operations into the compiled binary code. Further, instruction decoding in conventional dynamic binary translator is hierarchical and involves lots of control transfer whereas in template based translation it amounts to extracting certain bits from the input instruction to form the unique template ID. Due to these improvements template based translation offers a significant reduction in translation overhead.

The above embodiments are described with reference to the PA-RISC and Itanium platforms. However, embodiments of the invention include systems that operate between any platform or processor types. The source or target processors or code sets may be 32-bit or 64-bit, reduced instruction set processors (RISC), complex instruction set processors (CISC), explicitly parallel instruction processors (EPIC) or very large instruction word processors (VLIW).

Further embodiments operate to transform data in databases from one format to another, for example, when data stored in an old database is needed in an upgraded database. While the databases may similar in that they both store data elements in the same format, binary meta-data describing how that data is stored may be modified in the upgraded database to enable new features. To enable efficient migration between databases, data transformation routines are created to transform the meta-data from the old database to the upgraded database using the bit filling techniques described above.

It will be understood by those skilled in the art that the apparatus that embodies a part or all of the present invention may be a general purpose device having software arranged to provide a part or all of an embodiment of the invention. The device could be single device or a group of devices and the software could be a single program or a set of programs. Furthermore, any or all of the software used to implement the invention can be communicated via various transmission or storage means such as computer network, floppy disc, CD-ROM or magnetic tape so that the software can be loaded onto one or more devices.

While the present invention has been illustrated by the description of the embodiments thereof, and while the embodiments have been described in considerable detail, it is not the intention of the applicant to restrict or in any way limit the scope of the appended claims to such detail. Additional advantages and modifications will readily appear to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details representative apparatus and method, and illustrative examples shown and described. Accordingly, departures may be made from such details without departure from the spirit or scope of applicant's general inventive concept. 

1. A method for creating data transformation routines for binary data for transforming said data from a source format to a target format, the method comprising the steps of: a) generating a source model of a source format element; b) generating a target model of a target format element; c) generating a mapping between said source model and said target model; d) generating a transformation routine based on said mapping for extracting data from said source element and depositing said data in said target element.
 2. A method according to claim 1 in which target models are generated for a plurality of target elements and a mapping generated between the source model and said plurality of target models.
 3. A method according to claim 1 in which source models are generated for a plurality of source elements and a mapping generated between said plurality of source models and said target model.
 4. A method according to claim 1 in which said transformation routine is arranged for transforming data in software code instructions from a source format code to a target format code and said routines are generated in said target format code.
 5. A method according to claim 1 in which the mapping accounts for differences in endianness between the source and target models.
 6. A method according to claim 4 in which the transformation routine is executed at the runtime of a program in said source code.
 7. A method according to claim 1 in which said models relate bit positions to variable names for any given instruction.
 8. A method according to claim 1 in which a group of source models and target models are provided wherein one or more models are applicable to a plurality of respective source or target instructions.
 9. A method according to claim 4 in which said transformation routine is associated with a template providing a set of target format instructions semantically equivalent to said identified source instruction.
 10. A method according to claim 1 in which the transformation routine is arranged for transforming data from a database between a source database format to a target database format.
 11. Apparatus for creating data transformation routines for transforming data from a source format to a target format, the apparatus comprising: a) a source model of a source element; b) a target model of a target element; c) a mapping between said source model and said target model; d) a routine generator for generating a transformation routine based on said mapping for extracting data from said source element and depositing said data in the target element.
 12. Apparatus according to claim 11 further comprising target models for a plurality of target elements and a mapping between the source model and said plurality of target models.
 13. Apparatus according to claim 11 further comprising source models for a plurality of source elements and a mapping between said plurality of source models and said target model.
 14. A method according to claim 11 in which said transformation routine is arranged for transforming data in software code instructions from a source format code to a target format code and said routines are generated in said target format code.
 15. Apparatus according to claim 111 in which the mapping accounts for differences in endianness between the source and target models.
 16. Apparatus according to claim 14 in which the transformation routine is executed at the runtime of a program in said source code.
 17. Apparatus according to claim 11 in which said models relate bit positions to variable names for any given instruction.
 18. Apparatus according to claim 11 in which a group of source models and target models are provided wherein one or more models are applicable to a plurality of respective source or target instructions.
 19. Apparatus according to claim 14 in which said transformation routine is associated with a template providing a set of target format instructions semantically equivalent to said identified source instruction.
 20. Apparatus according to claim 11 in which the transformation routine is arranged for transforming data from a database between a source database format to a target database format.
 21. A computer program for transforming data from a source instruction to a target instruction, in accordance with the method of claim 1
 22. A computer program according to claim 21 in which said transformation routines are implemented as routines in said computer program.
 23. A computer program according to claim 21 operable to carry out said transformation at said runtime of a program in said source format. 